home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
oplkit14.zip
/
OPLKIT.DOC
< prev
next >
Wrap
Text File
|
1991-10-26
|
6KB
|
166 lines
OPUS LANGUAGE KIT
for Opus CBCS 1.1x & 1.7x
version 1.4
by Blagi
Copyright Blagi, 1991
Released to Public Domain.
OPUS CBCS LANGUAGE KIT consist of following files:
USL2OLT.EXE OPUS .USL to .OLT ASCII file
OLT2USL.EXE .OLT ASCII file to OPUS .USL
OPLKIT.DOC Description of OPUS Language Kit (this file)
OPLKIT.REV Revision history
archived into OPLKITxx.ZIP.
The purpose of OPUS LANGUAGE KIT is to help in translating .USL (OPUS
CBCS User Language with messages).
USL2OLT.EXE converts .USL file into ASCII file with extension .OLT (as
OPUS Language Translation). You can edit this file with some plain
ASCII editor and then convert it back to .USL file with OLT2USL.EXE.
Format of the .OLT file is similar to format of the .OEC files, e.g.
there are some keywords in square brackets([]) that are translation of
Opus Embedded Commands which are used in .USL file.
The following Keywords are recognized:
Keyword Ctrl key Hexadecimal Description
-------------------------------------------------------------------------
[bell] ^G x07 Ring the caller' bell
[bs] ^H x08 Backspace
[tab] ^I x09 Tab
[lf] ^J x0a Line feed
[cls] ^L x0c Clear screen
[cr] ^M x0d Carriage return
[can] ^X x18 Cancel
[esc] ^[ x1b Escape for ANSI/VT-100 seqence
[sp] x20 Space on the end of line
--- AVATAR Color codes:
[black] ^V^A^@ x16,x01,x00
[blue] ^V^A^A x16,x01,x01
[green] ^V^A^B x16,x01,x02
[cyan] ^V^A^C x16,x01,x03
[red] ^V^A^D x16,x01,x04
[magenta] ^V^A^E x16,x01,x05
[brown] ^V^A^F x16,x01,x06
[gray] ^V^A^G x16,x01,x07
[darkgray] ^V^A^H x16,x01,x08
[lightblue] ^V^A^I x16,x01,x09
[lightgreen] ^V^A^J x16,x01,x10
[lightcyan] ^V^A^K x16,x01,x11
[lightred] ^V^A^L x16,x01,x12
[lightmagenta] ^V^A^M x16,x01,x13
[yellow] ^V^A^N x16,x01,x14
[white] ^V^A^O x16,x01,x15
[blink] ^V^B x16,x02 Blinking
[cleol] ^V^G x16,x07 Clear to end of line
There are also two special keywords:
For repeating chars:
[repeat] ^Y x19 Repeat one char
The full format is:
[repeat][xxx][nn] ,
where xxx is ASCII decimal code, and nn is number of repetition.
For combination foregraund-background colours, the format is:
[FG-color on BG-color]
e.g: [yellow on black]
Left square bracket used in messages must be preeceded with left square
bracket. E.g. "More[Y,n]" in .USL is translated to "More[[Y,n]" in
.OLT file. Same rule must be followed in adding left square bracket
into .OLT file.
First record in .OLT file has a following format:
[V0000]v n
where: v is a version number of .USL file (e.g. 1 for Opus 1.1x, and
2 for Opus 1.7x
n is number of messages in .USL file
[V0000] is a constant
Don't change this record. If you have to change it when moving .OLT
file from one version to another do it carefully. If the .USL file
have wrong version number Opus will report LanguageERR.
Preceding every message in .OLT file there is a record number in
format:
[Nxxxx]
where xxxx is a decimal number with leading zeros.
For messages that points to xFFFF in .USL file, the contents of record
(line) is the message number only.
This version of OPUS Language Kit is for OPUS CBCS v.1.1x & 1.7x.
Unlike previous versions of Opus Language Kit number of messages are
not hard wired into program so it can support next releases of OPUS.
USL2OLT.EXE
-----------
This program converts .USL file into .OLT file. It is started with
following format:
USL2OLT <uslfile> [oltfile]
If no extension is specified for <uslfile> .USL is assumed.
If no extension is specified for [oltfile] .OLT is assumed.
If [oltfile] is omitted, <uslfile> path name with .OLT extension is
assumed.
OLT2USL.EXE
-----------
This program converts .OLT file into .USL file. It is started with
following format:
OLT2USL <oltfile> [uslfile]
If no extension is specified for <oltfile> .OLT is assumed.
If no extension is specified for [uslfile] .USL is assumed.
If [uslfile] is omitted, <oltfile> path name with .USL extension is
assumed.
Please keep the original version of .USL file because OLT2USL may
override it.
THANKS
------
Thanks to Fred Vlinkervleugel (2:281/603@fidonet) for using OPLKIT and
suggestion about space-on-the-end-of-line problem.
Thanks to Bengt Erik Soderstrom (2:204/410@fidonet) for discovering bug
in handling ASCII chars greater then 128.
NOTE
----
The structure of .USL files is not described in Opus.h file
"Because the language files directly affect the "friendly and legal"
aspects of Opus, so to make it slightly more difficult for the
unfriendly and illegal we don't explain how it works. "
[as said Doug Boone - member of Opus 1.20 development team].
Any question and suggestion are welcomed and can be Netmailed to:
Zdravko Blagdan
JUBAS BBS 2:2/900@fidonet
++38-58-561-043
Split, Yugoslavia
or posted to MEADOW echo.
In Split, 02. Oct 1991.